Use django-cors-headers in docs #973
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## master #973 +/- ##
=======================================
Coverage 96.55% 96.55%
=======================================
Files 31 31
Lines 1715 1715
=======================================
Hits 1656 1656
Misses 59 59 Continue to review full report at Codecov.
|
auvipy
approved these changes
Sep 2, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
References #411
Description of the Change
Change docs to use django-cors-headers instead of django-cors-middleware which has been archived as a repo. Django-cors-headers resumed maintenance.
Besides installation, INSTALLED_APPS and the rest stays the same (since django-cors-middleware was a fork).
Checklist
CHANGELOG.mdupdated (only for user relevant changes)AUTHORS